Repository navigation
Remove IAM user here.hfla - #218
Merged
Merged
Conversation
|
Terraform plan in terraform Plan: 0 to add, 0 to change, 3 to destroy.Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
- destroy
Terraform will perform the following actions:
# module.iam_user_herehfla.aws_iam_user.user will be destroyed
# (because aws_iam_user.user is not in configuration)
- resource "aws_iam_user" "user" {
- arn = "arn:aws:iam::035866691871:user/here.hfla" -> null
- force_destroy = true -> null
- id = "here.hfla" -> null
- name = "here.hfla" -> null
- path = "/" -> null
- tags = {
- "Access Level" = "1"
- "Project" = "devops-security"
} -> null
- tags_all = {
- "Access Level" = "1"
- "Project" = "devops-security"
- "managed-by" = "terraform-devops-security"
} -> null
- unique_id = "AIDAQQWOSJEPSJ2DCMAHY" -> null
# (1 unchanged attribute hidden)
}
# module.iam_user_herehfla.aws_iam_user_group_membership.user_group_membership will be destroyed
# (because aws_iam_user_group_membership.user_group_membership is not in configuration)
- resource "aws_iam_user_group_membership" "user_group_membership" {
- groups = [
- "read-only-group",
] -> null
- id = "terraform-aJORSVMK4GqQzwO28JhNS81ud4" -> null
- user = "here.hfla" -> null
}
# module.iam_user_herehfla.aws_iam_user_login_profile.user_login will be destroyed
# (because aws_iam_user_login_profile.user_login is not in configuration)
- resource "aws_iam_user_login_profile" "user_login" {
- id = "here.hfla" -> null
- password = (sensitive value) -> null
- password_length = 20 -> null
- password_reset_required = true -> null
- user = "here.hfla" -> null
}
Plan: 0 to add, 0 to change, 3 to destroy.✅ Plan applied in Apply Terraform changes on merge #54 |
Merged
ale210
pushed a commit
that referenced
this pull request
Oct 29, 2026
* Use S3 native state locking instead of DynamoDB (#218) Replace the deprecated dynamodb_table backend parameter with use_lockfile = true, drop the DynamoDB statement from the live IncubatorTfPlanSecretsRead policy, and remove the lock-table setup from CONTRIBUTING.md and the pre-work issue template. The backend.tf comment makes the terraform-plan/apply workflows trigger, since they only filter on **/*.tf. * Clarify changes migrating lockfiles to s3 from dynamodb Continues #218
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #205 (step 1 of 2: remove
here.hfla; a follow-up PR recreates the account ashere, the GitHub handle)What changes did you make?
iam_user_herehflamodule block fromterraform/aws-users.tfWhy did you make the changes (we will use this info to test)?
here, as the naming convention expects (the block still carried its# Replace with GitHub handleplaceholder)read-only-groupmembershipforce_destroyhas nothing extra to remove